OCPSTRAT-3661: Add Sippy discovered exceptions for RBAC monitor test - #31616
OCPSTRAT-3661: Add Sippy discovered exceptions for RBAC monitor test#31616JoelSpeed wants to merge 1 commit into
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
|
@JoelSpeed: This pull request references OCPSTRAT-3661 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Repository YAML (base), Central YAML (inherited) Review profile: CHILL Plan: Enterprise Run ID: 📒 Files selected for processing (2)
Included review availability: Your plan provides up to 12 included reviews per hour; 11 remain after this review. WalkthroughThe RBAC escalation monitor adds tracked exceptions for platform controllers and excludes ClusterRoleBindings generated by OLM ClusterServiceVersions. Tests verify that removing the OLM ownership label restores normal evaluation. ChangesRBAC escalation monitoring
Estimated code review effort: 2 (Simple) | ~10 minutes Merge Risk: ⚪ Minimal · up to This change adds RBAC-monitor exceptions and excludes CSV-owned OLM bindings while preserving evaluation for unlabeled bindings. The behavior is covered by targeted tests, with no remaining merge-readiness risk identified. 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: JoelSpeed The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
As you reviewed the first part of this |
|
Scheduling required tests: |
|
@JoelSpeed: The following test failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This extends the tests added in #31536 based on new findings from Sippy
Also excludes OLM installed operators that have been picked up in tests where these do not have predictable names and cannot be added to the exceptions list cleanly
Summary by CodeRabbit